Skip to content

Conversation

@keynslug
Copy link
Contributor

See also emqx/emqx#16123.

@keynslug keynslug added this to the 6.0.1 milestone Oct 14, 2025
@keynslug keynslug requested a review from zmstone October 15, 2025 16:14
Meggielqk
Meggielqk previously approved these changes Nov 7, 2025
@Meggielqk Meggielqk requested a review from Copilot November 7, 2025 09:42
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds documentation for a known issue regarding replicant node startup failures when new core nodes are added to EMQX clusters. The issue, which existed since version 5.1.0 and was fixed in 6.0.1, is now documented in both the 5.9 and 6.0 known issues files for English and Chinese documentation.

  • Adds new known issue entry about replicant node startup hangs during cluster expansion
  • Fixes spelling error "invervention" → "intervention" in existing 6.0 entry
  • Updates table formatting to include status information

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File Description
en_US/changes/known-issues-6.0.md Adds replicant node startup issue, fixes spelling in existing bridge upgrade issue
en_US/changes/known-issues-5.9.md Adds replicant node startup issue to 5.9 known issues
zh_CN/changes/known-issues-6.0.md Chinese translation of the same changes as English 6.0 file
zh_CN/changes/known-issues-5.9.md Chinese translation of the same changes as English 5.9 file

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@id id merged commit e7a02c4 into emqx:release-6.0 Nov 7, 2025
4 of 6 checks passed
@keynslug keynslug deleted the chore/mria-0.8.18/known-issue branch November 7, 2025 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants